Messagebroker feature - #807

Move the base adapter and data models into a lightweight package, add
execution-free model definitions, and switch the existing API implementation to
the shared contracts.

Introduce typed adapter jobs, results, heartbeats, and queue naming

Implement durable publishing, acknowledged consumption, result
dead-letter topology, and explicit structural typing checks.

Ensured this works with mypy for the protocols

Provide the message broker communication for each of the adapters

Make it possible to detect if there are workers alive (or if we need to
wait for them to be started)

We add a listener to the results queue who will only ensure that as
messages are coming in from the models, the result is persisted in the
database and if necessary publish the next job.

We start all the backend services from the same location, making it
obvious how many there are.

Utilise the new messagebroker setup to publish simulations from the web
endpoints

Have the models run in-process instead of using web api (all but phpitz)
We ensure that there is a single adapter specification, hence the
workers are not depending on acidwatch_models

Add the heartbeat result in the simulations endpoint response, so that
caller side can know if the simulations are being worked on or not.

uv is not included in the production image, let's just run the commands
from the python env directly.